An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

I recently had an app rejected for 2.1 - Performance - App Completeness and specifically, “no subscription options available“. The previous build I submitted did have the issue, but this latest one did not, at least as far as I could test. I tested on two different devices using a sandbox account as well as TestFlight and the IAP were visible and working. I also see each IAP pop up correctly within RevenueCat. One thing that may be an issue is I don’t have the section to attach the IAP onto the build before submitting to review. I’ve read through every help article I could find and have triple-checked everything with the IAP is in order. Pricing, localization, screenshot, review notes, signed agreement, etc. I’ve also tried reaching out several times through the contact us page as well as replied to the review, but haven’t received a response. Is there anything I could be missing? Is not attaching them to the build the issue and if so, how can I get them to show up without recreating the IAP with new names? Thank you.

Hey all, I am a first time publisher navigating the App Review process. I want to publish a watchOS only app, but keep getting this feedback: Regarding 4.0, Apple Watch app icon's background color is still black. Based on our investigation, you have included plain black icons. To resolve this issue, it would be appropriate to modify your app's Apple Watch app icon to include a lighter background color to ensure that it is recognizable and appears circular on Apple Watch. I set the following configs: Project -> Targets -> Apple Watch App -> App Icons & Launch Screen -> App Icon set to my Icon Composer file. Checked App Icons Source. I was able to install my build through TestFlight and successfully install on my watch, and the App Icon displays properly there. I also saw a recent Reddit post from another developer facing the same issue. I can't link that post, but will share this post with the OP. I attached what the reviewer sent me with the rejection.

My app (App ID: 6757516331) has been stuck in "Waiting for Review" since February 3rd. It has been over a week, and I have not received any updates yet. Any assistance would be greatly appreciated. Thank you.

Hi, Got my first submission rejected due to Design - Minimum Functionality and would like to ask for some guidance on what to do. To give some context of my app. My app is quite simple but solves a common issue in my home town. During the winter month, every street will have a certain time when parking is forbidden. This results in everyone having to move their car several times a week to avoid getting tickets. Every time you move, you need to note and remember when to move it again, etc. A parking ticket for forgetting is around 140 USD. My app aims to solve this by letting the user press a button which makes the app use the current GPS location to fetch the parking relevant parking restriction and create a notification the day before, reminding the user to move their car. Simple UI and nothing fancy. I've also created onboarding that gives relevant information the first time a user open their app. I'm a bit on the fence on what I should do to pass. In my opinion, the functionality is more than a website because it uses GPS, creates notifications, loading spinner when parking restrictions are being fetched, has onboarding, etc. I think an issue that might cause the reviewer to dismiss it is that it currently only work in my specific town - it uses certain APIs to fetch the parking restrictions. So, should I try to create more functionality (not sure what) or do I need to clearly argue my case and demo my apps functionality via recordings? Thanks in advance for any help and guidance :)

Hello, I’m looking for guidance regarding a new app submission that has been in “Waiting for Review” status for 6 days now, with no change or additional communication. This is a brand-new app submission (not an update). There have been no metadata changes or rejections — it has remained in the waiting state since submission. I completely understand that review times can vary depending on workload and complexity. I just wanted to check whether this timeframe is currently normal, or if there may be something specific I should verify on my end. The app is an educational medical application, and all content is original. There are no unusual entitlements, external payment systems, or restricted APIs involved. If anyone from Apple or fellow developers has insight into whether extended “Waiting for Review” times are currently common, I would appreciate your input. Thank you in advance.

My app has been in “Waiting for Review” since January 31. I already submitted a support case (id - 102819325365) last week, but haven’t received a response. I also requested an expedited review but with no response either. This is not a new app, and all previous submissions were completed in less than 48 hours, so this delay seems unusual.

Hello, My new app (App ID: 6757254070) has remained in the “Waiting for Review” status since February 1 (UTC+9). Because the review process seemed to be taking unusually long compared to my previous experiences, I submitted an inquiry (Reference ID: 102812788306), but I have not yet received any response. For additional context, the app was originally submitted on January 23 and remained in the “Waiting for Review” state for eight days. As I was concerned there might have been an issue with the review queue, I canceled the submission and resubmitted the app on February 1. At this point, I am wondering whether the prolonged waiting time is simply due to a heavy backlog in the App Review process. Thank you very much for taking the time to read this. I hope you have a great day.

I needed to change the bundleid in my app, so I created a new app and used the build I created with the same source code and deleted my old app completely, but my app is rejected for spam

Hi, I'm here hoping for some help or advice in terms of a critical situation I'm currently facing. I've submitted an iOS app more than one month ago, it was quickly got review and rejected twice, and when I re-submit the third time with new build, it then was stuck in the "Waiting for review" status for about 3 weeks. Then, I decided to withdraw the submission and re-submit again, but it doesn't work and remain "Waiting for review" status until now. During these waiting period, I’ve contacted Apple Support multiple times through mails, and received confirmation that my expedited review request was approved. However, no progress has been made since then. Here is a quick summary of the timeline Initial submission: July 29, 2025 Rejected due to Guideline 4.2.2 & 2.1: July 30, 2025 Second submission: Aug 4, 2025 Rejected due to Guideline 4.2.2 & 4.2.0: Aug 6, 2025 Third submission: Aug 6, 2025 Withdraw third & create forth submission: Aug 25, 2025 If anyone from the App Review team sees this post, or if any developers have experienced a similar situation and can offer advice, we would be truly grateful. Thank you in advance for your time and support.

Hi! Our app has been rejected several times now. We first selected the "made for kids" category because that was the age recommended by apple. Everything went fine at first but now, two updated later, we are starting to get rejected. We unchecked the made for kids box but even after that we are still not getting approved. We have tried to explain our issue to apple support but they aren't giving us any good answers. Is there any way to resolve this issue? We are really in the need of help.

Hello everyone, I wanted to check if anyone else has experienced longer App Review delays recently. Our recent app submission has been in the “In Review” status for more than 7 days (since Jan 15, 10:44 PM). In our previous submissions, reviews usually started or completed within a few days, so this delay feels unusual. Current situation: No messages or rejection notes from Apple No metadata or compliance issues flagged Status remains “In Review” without updates I’d appreciate guidance from the community: • Is this type of delay normal these days? • Could this indicate a manual or extended review? • At what point should we contact App Review directly? • What is the best way to contact App Store / App Review support regarding a stuck review? If anyone has faced a similar delay and can share their experience or advice, it would be very helpful. Thank you in advance for your help.

Hello, We have applied for the Apple Developer Program under a government organization account. After submitting the enrollment, we received a confirmation email stating that the request was received and that we would be contacted after verification of authorization to bind the organization to the Apple Developer Program legal agreements. However, it has been quite some time, and we have not received any further updates regarding the verification process. We would like to understand: What is the usual verification timeline for government organizations? Is extended verification common for government entities? Is there anything additional we should do from our side to help move the process forward? If anyone has experienced a similar situation or can share guidance, it would be greatly appreciated. Thank you.

I recently released the first version of my app, and it was discoverable via App Store search. After pushing an update with bug fixes and improved keywords/category, the new version went live and showed as “Ready for Sale” within hours. However, since the update, the app no longer appears in App Store search results - even when searched using its exact name. It’s still accessible through the direct link. Any insights or guidance would be greatly appreciated!

I have been exploring App Store Optimization and noticed that Apple primarily uses the App Name, Subtitle, and Keyword field as the main text based ranking signals according to official and third party sources. Are these the only factors that truly impact iOS ASO, or do elements like the app description and promotional text indirectly influence visibility, conversion, or ranking updates over time, and how frequently should subtitles and keywords be revised after launch.

When I update my app name, the App Store URL also changes, and since the app URL contributes to ASO performance, this is a concern for me. I would like to know whether it is possible to change the app name without affecting the URL, or if the previous URL automatically redirects to the new one.

I see many developers struggling with ASO where AI written content does not deliver results, performance analysis is unclear, localization is ignored, App Store optimization is incomplete, and keywords are often poorly chosen. I am considering running two simple group sessions to share practical tips and show clear ways to improve ASO with real effort involved, and I would like feedback on this idea whether offered for a small fee or even for free.

Hello, With the recent update to Guideline 1.2 stating apps used primarily for “anonymous chat” may be removed, could App Review clarify what “anonymous” means in this context? In our app, users interact using a chosen username and avatar. We don’t display legal names publicly, but each user has a persistent, verified account and all UGC is tied to that account so we can enforce bans. We also provide filtering, reporting, and blocking. Question: Do applications that provide chat functionality with pseudonymous users — meaning users do not display their real names — have the right to exist under this guideline, provided that accounts are persistent and enforceable? If anyone has recently passed review with a similar pseudonymous chat model, I’d appreciate any guidance on how you framed 1.2 compliance.

My app was reviewed and approved on Feb 3rd, and still does not show in app store. I have submitted a ticket to Apple Feb 3rd, and still have not received a reply. I get either 404, or "this app is not available your country or region". This does it for me, and anyone I've asked to try it. This is very confusing - please someone help! https://apps.apple.com/us/app/exp-lights/id6758403863